Playback device volume management

ABSTRACT

Embodiments are described herein that provide numerous volume enhancements to a media playback system. An example implementation involves a playback device playing audio content at a first volume level as part of a first audio playback group configuration, storing a first volume level in association with the first audio playback group configuration, joining a second audio playback group configuration, playing audio content at a second volume level as a part of the second audio playback group configuration, receiving a command to play audio content as part of the first audio playback group configuration, identifying the first volume level in the data storage; and playing audio content at the first volume level as part of the first audio playback group configuration.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 120 to, and is acontinuation of, U.S. non-provisional patent application Ser. No.14/039,312, filed on Sep. 27, 2013, entitled “Volume Enhancements in aMulti-Zone Media Playback System,” which is incorporated herein byreference.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer goods and, more particularly, tomethods, systems, products, features, services, and other items directedto media playback or some aspect thereof.

BACKGROUND

Digital music has become readily available due in part to thedevelopment of consumer level technology that has allowed people tolisten to digital music on a personal audio device. The consumer'sincreasing preference for digital audio has also resulted in theintegration of personal audio devices into PDAs, cellular phones, andother mobile devices. The portability of these mobile devices hasenabled people to take the music listening experience with them andoutside of the home. People have also become able to consume digitalmusic, like digital music files or even Internet radio, in the homethrough the use of their computer or similar devices. Now there are manydifferent ways to consume digital music, in addition to other digitalcontent including digital video and photos, stimulated in many ways byhigh-speed Internet access at home, mobile broadband Internet access,and the consumer's hunger for digital media.

Until recently, options for accessing and listening to digital audio inan out-loud setting were severely limited. In 2005, Sonos offered forsale its first digital audio system that enabled people to, among manyother things, access virtually unlimited sources of audio via one ormore networked connected zone players, dynamically group or ungroup zoneplayers upon command, wirelessly send the audio over a local networkamongst zone players, and play the digital audio out loud acrossmultiple zone players in synchrony. The Sonos system can be controlledby software applications running on network capable mobile devices andcomputers.

Given the insatiable appetite of consumers towards digital media, therecontinues to be a need to develop consumer technology thatrevolutionizes the way people access and consume digital media.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologymay be better understood with regard to the following description,appended claims, and accompanying drawings where:

FIG. 1 shows an example configuration in which certain embodiments maybe practiced;

FIG. 2A shows an illustration of an example zone player having built-inamplifiers and transducers;

FIG. 2B shows an illustration of an example zone player having abuilt-in amplifier and connected to external speakers;

FIG. 2C shows an illustration of an example zone player connected to anA/V receiver and speakers;

FIG. 3 shows an illustration of an example controller;

FIG. 4 shows an internal functional block diagram of an example zoneplayer;

FIG. 5 shows an internal functional block diagram of an examplecontroller;

FIG. 6 shows an example playback queue configuration for a mediaplayback system;

FIG. 7 shows an example ad-hoc playback network;

FIG. 8 shows a system including a plurality of networks including acloud-based network and at least one media playback system;

FIG. 9 shows an example system diagram for illustrating several volumeenhancement embodiments;

FIG. 10 shows an example process for setting a zone player volume levelsubsequent from removing the zone player from a group;

FIG. 11 shows an example process for setting a zone player volume levelsubsequent to grouping the zone player; and

FIG. 12 shows an example process for setting a volume level of each zoneplayer in a group.

In addition, the drawings are for the purpose of illustrating exampleembodiments, but it is understood that the inventions are not limited tothe arrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

Embodiments described herein are directed to numerous volumeenhancements for a media playback system, and are particularly useful ina multi-zone media playback system, where zone players are capable ofbeing grouped to form one or more synchronous audio playback groups. Amedia playback system that provides a user with the option via acontroller to dynamically group and ungroup various zone players is adesirable feature, but calls for management of different systemvariables, such as volume level(s). The present application describesvolume enhancements that significantly improve volume setting in suchsystems.

II. Example Operating Environment

Referring now to the drawings, in which like numerals can refer to likeparts throughout the figures, FIG. 1 shows an example media playbacksystem configuration 100 in which one or more embodiments disclosedherein can be practiced or implemented.

By way of illustration, the media playback system configuration 100 isassociated with a home having multiple zones, although it should beunderstood that the home could be configured with only one zone.Additionally, one or more zones can be added to the configuration 100over time. Each zone may be assigned by a user to a different room orspace, such as, for example, an office, bathroom, bedroom, kitchen,dining room, family room, home theater room, utility or laundry room,and patio. A single zone might also include multiple rooms or spaces ifso configured. With respect to FIG. 1, one or more of zone players102-124 are shown in each respective zone. Zone players 102-124, alsoreferred to herein as playback devices, multimedia units, speakers,players, and so on, provide audio, video, and/or audiovisual output. Acontroller 130 (e.g., shown in the kitchen for purposes of thisillustration) provides control to the media system configuration 100.Controller 130 may be fixed to a zone, or alternatively, mobile suchthat it can be moved about the zones. The media system configuration 100may also include more than one controller 130, and additionalcontrollers may be added to the system over time.

The media system configuration 100 illustrates an example whole housemedia system, though it is understood that the technology describedherein is not limited to, among other things, its particular place ofapplication or to an expansive system like a whole house media system100 of FIG. 1.

a. Example Zone Players

FIGS. 2A, 2B, and 2C show example types of zone players. Zone players200, 202, and 204 of FIGS. 2A, 2B, and 2C, respectively, can correspondto any of the zone players 102-124 of FIG. 1, for example. In someembodiments, audio is reproduced using only a single zone player, suchas by a full-range player. In some embodiments, audio is reproducedusing two or more zone players, such as by using a combination offull-range players or a combination of full-range and specializedplayers. In some embodiments, zone players 200-204 may also be referredto as a “smart speaker,” because they contain processing capabilitiesbeyond the reproduction of audio, more of which is described below.

FIG. 2A illustrates a zone player 200 that includes sound producingequipment 208 capable of reproducing full-range sound. The sound maycome from an audio signal that is received and processed by zone player200 over a wired or wireless data network. Sound producing equipment 208includes one or more built-in amplifiers and one or more acoustictransducers (e.g., speakers). A built-in amplifier is described morebelow with respect to FIG. 4. A speaker or acoustic transducer caninclude, for example, any of a tweeter, a mid-range driver, a low-rangedriver, and a subwoofer. In some embodiments, zone player 200 can bestatically or dynamically configured to play stereophonic audio,monaural audio, or both. In some embodiments, zone player 200 may bedynamically configured to reproduce a subset of full-range sound, suchas when zone player 200 is grouped with other zone players to playstereophonic audio, monaural audio, and/or surround audio or when themedia content received by zone player 200 is less than full-range.

FIG. 2B illustrates zone player 202 that includes a built-in amplifierto power a set of detached speakers 210. A detached speaker can include,for example, any type of loudspeaker. Zone player 202 may be configuredto power one, two, or more separate loudspeakers. Zone player 202 may beconfigured to communicate an audio signal (e.g., right and left channelaudio or more channels depending on its configuration) to the detachedspeakers 210 via a wired path.

FIG. 2C illustrates zone player 204 that does not include a built-inamplifier, but is configured to communicate an audio signal, receivedover a data network, to an audio (or “audio/video”) receiver 214 withbuilt-in amplification.

Referring back to FIG. 1, in some embodiments, one, some, or all of thezone players 102 to 124 can retrieve audio directly from a source. Forexample, a particular zone player in a zone or zone group may beassigned to a playback queue (or “queue”). The playback queue containsinformation corresponding to zero or more audio items for playback bythe associated zone or zone group. The playback queue may be stored inmemory on a zone player or some other designated device. Each itemcontained in the playback queue may comprise a uniform resourceidentifier (URI) or some other identifier that can be used by the zoneplayer(s) to seek out and/or retrieve the audio items from theidentified audio source(s). Depending on the item, the audio sourcemight be found on the Internet (e.g., the cloud), locally from anotherdevice over the data network 128 (described further below), from thecontroller 130, stored on the zone player itself, or from an audiosource communicating directly to the zone player. In some embodiments,the zone player can reproduce the audio itself (e.g., play the audio),send the audio to another zone player for reproduction, or both wherethe audio is reproduced by the zone player as well as one or moreadditional zone players (possibly in synchrony). In some embodiments,the zone player may play a first audio content (or alternatively, maynot play the content at all), while sending a second, different audiocontent to another zone player(s) for reproduction. To the user, eachitem in a playback queue is represented on an interface of a controllerby an element such as a track name, album name, radio station name,playlist, or other some other representation. A user can populate theplayback queue with audio items of interest. The user may also modifyand clear the playback queue, if so desired.

By way of illustration, SONOS, Inc. of Santa Barbara, Calif. presentlyoffers for sale zone players referred to as a “PLAY:5,” “PLAY:3,”“PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any other past, present,and/or future zone players can additionally or alternatively be used toimplement the zone players of example embodiments disclosed herein.Additionally, it is understood that a zone player is not limited to theparticular examples illustrated in FIGS. 2A, 2B, and 2C or to the SONOSproduct offerings. For example, a zone player may include a wired orwireless headphone. In yet another example, a zone player may include orinteract with a docking station for an Apple iPod™ or similar device.

b. Example Controllers

FIG. 3 illustrates an example wireless controller 300 in docking station302. By way of illustration, controller 300 may correspond tocontrolling device 130 of FIG. 1. Docking station 302, if provided orused, may provide power to the controller 300 and additionally maycharge a battery of controller 300. In some embodiments, controller 300may be provided with a touch screen 304 that allows a user to interactthrough touch with the controller 300, for example, to retrieve andnavigate a playlist of audio items, modify and/or clear the playbackqueue of one or more zone players, control other operations of one ormore zone players, and provide overall control of the systemconfiguration 100. In other embodiments, other input mechanisms such asvoice control may be used to interact with the controller 300. Incertain embodiments, any number of controllers can be used to controlthe system configuration 100. In some embodiments, there may be a limitset on the number of controllers that can control the systemconfiguration 100. The controllers might be wireless like wirelesscontroller 300 or wired to data network 128.

In some embodiments, if more than one controller is used in system 100of FIG. 1, each controller may be coordinated to display common content,and may all be dynamically updated to indicate changes made to thesystem 100 from a single controller. Coordination can occur, forinstance, by a controller periodically requesting a state variabledirectly or indirectly from one or more of the zone players; the statevariable may provide information about system 100, such as current zonegroup configuration, what is playing in one or more zones, volumelevels, and other items of interest. The state variable may be passedaround on data network 128 between zone players (and controllers, if sodesired) as needed or as often as programmed.

In addition, an application running on any network-enabled portabledevice, such as an iPhone™, iPad™, Android™ powered phone or tablet, orany other smart phone or network-enabled device can be used ascontroller 130. An application running on a laptop or desktop personalcomputer (PC) or Mac™ can also be used as controller 130. Suchcontrollers may connect to system 100 through an interface with datanetwork 128, a zone player, a wireless router, or using some otherconfigured connection path. Example controllers, which have been offeredby Sonos, Inc. of Santa Barbara, Calif. include a “Controller 200,”“SONOS® CONTROL,” “SONOS® Controller for iPhone™,” “SONOS® Controllerfor iPad™,” “SONOS® Controller for Android™,” “SONOS® Controller forMac™ or PC.”

c. Example Data Connection

Zone players 102-124 of FIG. 1 are coupled directly or indirectly to adata network, such as data network 128. Controller 130 may also becoupled directly or indirectly to data network 128 or individual zoneplayers. Data network 128 is represented by an octagon in the figure tostand out from other representative components. While data network 128is shown in a single location, it is understood that such a network isdistributed in and around system 100. Particularly, data network 128 canbe a wired network, a wireless network, or a combination of both wiredand wireless networks. In some embodiments, one or more of the zoneplayers 102-124 are wirelessly coupled to data network 128 based on aproprietary mesh network. In some embodiments, one or more of the zoneplayers are coupled to data network 128 using a centralized access pointsuch as a wired or wireless router. In some embodiments, one or more ofthe zone players 102-124 are coupled via a wire to data network 128using Ethernet or similar technology. In addition to the one or morezone players 102-124 connecting to data network 128, data network 128can further allow access to a wide area network, such as the Internet.

In some embodiments, connecting any of the zone players 102-124, or someother connecting device, to a broadband router, can create data network128. Other zone players 102-124 can then be added wired or wirelessly tothe data network 128. For example, a zone player (e.g., any of zoneplayers 102-124) can be added to the system configuration 100 by simplypressing a button on the zone player itself (or perform some otheraction), which enables a connection to be made to data network 128. Thebroadband router can be connected to an Internet Service Provider (ISP),for example. The broadband router can be used to form another datanetwork within the system configuration 100, which can be used in otherapplications (e.g., web surfing). Data network 128 can also be used inother applications, if so programmed. An example, second network mayimplement SONOSNET™ protocol, developed by SONOS, Inc. of Santa Barbara.SONOSNET™ represents a type of secure, AES-encrypted, peer-to-peerwireless mesh network. Alternatively, in certain embodiments, the datanetwork 128 is the same network, such as a traditional wired or wirelessnetwork, used for other applications in the household.

d. Example Zone Configurations

A particular zone can contain one or more zone players. For example, thefamily room of FIG. 1 contains two zone players 106 and 108, while thekitchen is shown with one zone player 102. In another example, the hometheater room contains additional zone players to play audio from a 5.1channel or greater audio source (e.g., a movie encoded with 5.1 orgreater audio channels). In some embodiments, one can position a zoneplayer in a room or space and assign the zone player to a new orexisting zone via controller 130. As such, zones may be created,combined with another zone, removed, and given a specific name (e.g.,“Kitchen”), if so desired and programmed to do so with controller 130.Moreover, in some embodiments, zone configurations may be dynamicallychanged even after being configured using controller 130 or some othermechanism.

In some embodiments, a “bonded zone” contains two or more zone players,such as the two zone players 106 and 108 in the family room, whereby thetwo zone players 106 and 108 can be configured to play the same audiosource in synchrony. In one example, the two zone players 106 and 108can be paired to play two separate sounds in left and right channels,for example. In other words, the stereo effects of a sound can bereproduced or enhanced through the two zone players 106 and 108, one forthe left sound and the other for the right sound. In another example twoor more zone players can be sonically consolidated to form a single,consolidated zone player. A consolidated zone player (though made up ofmultiple, separate devices) can be configured to process and reproducesound differently than an unconsolidated zone player or zone playersthat are paired, because a consolidated zone player has additionalspeaker drivers from which sound can be passed. The consolidated zoneplayer can further be paired with a single zone player or yet anotherconsolidated zone player. Each playback device of a consolidatedplayback device can be set in a consolidated mode, for example.

In certain embodiments, paired or consolidated zone players (alsoreferred to as “bonded zone players”) can play audio in synchrony withother zone players in the same or different zones.

According to some embodiments, one can continue to do any of: group,consolidate, and pair zone players, for example, until a desiredconfiguration is complete. The actions of grouping, consolidation, andpairing are preferably performed through a control interface, such asusing controller 130, and not by physically connecting and re-connectingspeaker wire, for example, to individual, discrete speakers to createdifferent configurations. As such, certain embodiments described hereinprovide a more flexible and dynamic platform through which soundreproduction can be offered to the end-user.

e. Example Audio Sources

In some embodiments, each zone can play from the same audio source asanother zone or each zone can play from a different audio source. Forexample, someone can be grilling on the patio and listening to jazzmusic via zone player 124, while someone is preparing food in thekitchen and listening to classical music via zone player 102. Further,someone can be in the office listening to the same jazz music via zoneplayer 110 that is playing on the patio via zone player 124. In someembodiments, the jazz music played via zone players 110 and 124 isplayed in synchrony. Synchronizing playback amongst zones allows for anindividual to pass through zones while seamlessly (or substantiallyseamlessly) listening to the audio. Further, zones can be put into a“party mode” such that all associated zones will play audio insynchrony.

Sources of audio content to be played by zone players 102-124 arenumerous. In some embodiments, audio on a zone player itself may beaccessed and played. In some embodiments, audio on a controller may beaccessed via the data network 128 and played. In some embodiments, musicfrom a personal library stored on a computer or networked-attachedstorage (NAS) may be accessed via the data network 128 and played. Insome embodiments, Internet radio stations, shows, and podcasts may beaccessed via the data network 128 and played. Music or cloud servicesthat let a user stream and/or download music and audio content may beaccessed via the data network 128 and played. Further, music may beobtained from traditional sources, such as a turntable or CD player, viaa line-in connection to a zone player, for example. Audio content mayalso be accessed using a different protocol, such as Airplay™, which isa wireless technology by Apple, Inc., for example. Audio contentreceived from one or more sources can be shared amongst the zone players102 to 124 via data network 128 and/or controller 130. Theabove-disclosed sources of audio content are referred to herein asnetwork-based audio information sources. However, network-based audioinformation sources are not limited thereto.

In some embodiments, the example home theater zone players 116, 118, 120are coupled to an audio information source such as a television 132. Insome examples, the television 132 is used as a source of audio for thehome theater zone players 116, 118, 120, while in other examples audioinformation from the television 132 may be shared with any of the zoneplayers 102-124 in the audio system 100.

III. Example Zone Players

Referring now to FIG. 4, there is shown an example block diagram of azone player 400 in accordance with an embodiment. Zone player 400includes a network interface 402, a processor 408, a memory 410, anaudio processing component 412, one or more modules 414, an audioamplifier 416, and a speaker unit 418 coupled to the audio amplifier416. FIG. 2A shows an example illustration of such a zone player. Othertypes of zone players may not include the speaker unit 418 (e.g., suchas shown in FIG. 2B) or the audio amplifier 416 (e.g., such as shown inFIG. 2C). Further, it is contemplated that the zone player 400 can beintegrated into another component. For example, the zone player 400could be constructed as part of a television, lighting, or some otherdevice for indoor or outdoor use.

In some embodiments, network interface 402 facilitates a data flowbetween zone player 400 and other devices on a data network 128. In someembodiments, in addition to getting audio from another zone player ordevice on data network 128, zone player 400 may access audio directlyfrom the audio source, such as over a wide area network or on the localnetwork. In some embodiments, the network interface 402 can furtherhandle the address part of each packet so that it gets to the rightdestination or intercepts packets destined for the zone player 400.Accordingly, in certain embodiments, each of the packets includes anInternet Protocol (IP)-based source address as well as an IP-baseddestination address.

In some embodiments, network interface 402 can include one or both of awireless interface 404 and a wired interface 406. The wireless interface404, also referred to as a radio frequency (RF) interface, providesnetwork interface functions for the zone player 400 to wirelesslycommunicate with other devices (e.g., other zone player(s), speaker(s),receiver(s), component(s) associated with the data network 128, and soon) in accordance with a communication protocol (e.g., any wirelessstandard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac,802.15, 4G mobile communication standard, and so on). Wireless interface404 may include one or more radios. To receive wireless signals and toprovide the wireless signals to the wireless interface 404 and totransmit wireless signals, the zone player 400 includes one or moreantennas 420. The wired interface 406 provides network interfacefunctions for the zone player 400 to communicate over a wire with otherdevices in accordance with a communication protocol (e.g., IEEE 802.3).In some embodiments, a zone player includes multiple wireless 404interfaces. In some embodiments, a zone player includes multiple wired406 interfaces. In some embodiments, a zone player includes both of theinterfaces 404 and 406. In some embodiments, a zone player 400 includesonly the wireless interface 404 or the wired interface 406.

In some embodiments, the processor 408 is a clock-driven electronicdevice that is configured to process input data according toinstructions stored in memory 410. The memory 410 is data storage thatcan be loaded with one or more software module(s) 414, which can beexecuted by the processor 408 to achieve certain tasks. In theillustrated embodiment, the memory 410 is a tangible machine-readablemedium storing instructions that can be executed by the processor 408.In some embodiments, a task might be for the zone player 400 to retrieveaudio data from another zone player or a device on a network (e.g.,using a uniform resource locator (URL) or some other identifier). Insome embodiments, a task may be for the zone player 400 to send audiodata to another zone player or device on a network. In some embodiments,a task may be for the zone player 400 to synchronize playback of audiowith one or more additional zone players. In some embodiments, a taskmay be to pair the zone player 400 with one or more zone players tocreate a multi-channel audio environment. Additional or alternativetasks can be achieved via the one or more software module(s) 414 and theprocessor 408.

The audio processing component 412 can include one or moredigital-to-analog converters (DAC), an audio preprocessing component, anaudio enhancement component or a digital signal processor, and so on. Insome embodiments, the audio processing component 412 may be part ofprocessor 408. In some embodiments, the audio that is retrieved via thenetwork interface 402 is processed and/or intentionally altered by theaudio processing component 412. Further, the audio processing component412 can produce analog audio signals. The processed analog audio signalsare then provided to the audio amplifier 416 for playback throughspeakers 418. In addition, the audio processing component 412 caninclude circuitry to process analog or digital signals as inputs to playfrom zone player 400, send to another zone player on a network, or bothplay and send to another zone player on the network. An example inputincludes a line-in connection (e.g., an auto-detecting 3.5 mm audioline-in connection).

The audio amplifier 416 is a device(s) that amplifies audio signals to alevel for driving one or more speakers 418. The one or more speakers 418can include an individual transducer (e.g., a “driver”) or a completespeaker system that includes an enclosure including one or more drivers.A particular driver can be a subwoofer (e.g., for low frequencies), amid-range driver (e.g., for middle frequencies), and a tweeter (e.g.,for high frequencies), for example. An enclosure can be sealed orported, for example. Each transducer may be driven by its own individualamplifier.

A commercial example, presently known as the PLAY:5™, is a zone playerwith a built-in amplifier and speakers that is capable of retrievingaudio directly from the source, such as on the Internet or on the localnetwork, for example. In particular, the PLAY:5™ is a five-amp,five-driver speaker system that includes two tweeters, two mid-rangedrivers, and one woofer. When playing audio content via the PLAY:5, theleft audio data of a track is sent out of the left tweeter and leftmid-range driver, the right audio data of a track is sent out of theright tweeter and the right mid-range driver, and mono bass is sent outof the subwoofer. Further, both mid-range drivers and both tweeters havethe same equalization (or substantially the same equalization). That is,they are both sent the same frequencies but from different channels ofaudio. Audio from Internet radio stations, online music and videoservices, downloaded music, analog audio inputs, television, DVD, and soon, can be played from the PLAY:5™.

IV. Example Controller

Referring now to FIG. 5, there is shown an example block diagram forcontroller 500, which can correspond to the controlling device 130 inFIG. 1. Controller 500 can be used to facilitate the control ofmulti-media applications, automation and others in a system. Inparticular, the controller 500 may be configured to facilitate aselection of a plurality of audio sources available on the network andenable control of one or more zone players (e.g., the zone players102-124 in FIG. 1) through a wireless or wired network interface 508.According to one embodiment, the wireless communications is based on anindustry standard (e.g., infrared, radio, wireless standards includingIEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11 ac, 802.15, 4G mobilecommunication standard, and so on). Further, when a particular audio isbeing accessed via the controller 500 or being played via a zone player,a picture (e.g., album art) or any other data, associated with the audioand/or audio source can be transmitted from a zone player or otherelectronic device to controller 500 for display.

Controller 500 is provided with a screen 502 and an input interface 514that allows a user to interact with the controller 500, for example, tonavigate a playlist of many multimedia items and to control operationsof one or more zone players. The screen 502 on the controller 500 can bean LCD screen, for example. The screen 500 communicates with and iscommanded by a screen driver 504 that is controlled by a microcontroller(e.g., a processor) 506. The memory 510 can be loaded with one or moreapplication modules 512 that can be executed by the microcontroller 506with or without a user input via the user interface 514 to achievecertain tasks. In some embodiments, an application module 512 isconfigured to facilitate grouping a number of selected zone players intoa zone group to facilitate synchronized playback amongst the zoneplayers in the zone group. In some embodiments, an application module512 is configured to control the audio sounds (e.g., volume) of the zoneplayers in a zone group. In operation, when the microcontroller 506executes one or more of the application modules 512, the screen driver504 generates control signals to drive the screen 502 to display anapplication specific user interface accordingly.

The controller 500 includes a network interface 508 that facilitateswired or wireless communication with a zone player. In some embodiments,the commands such as volume control and audio playback synchronizationare sent via the network interface 508. In some embodiments, a savedzone group configuration is transmitted between a zone player and acontroller via the network interface 508. The controller 500 can controlone or more zone players, such as 102-124 of FIG. 1. There can be morethan one controller for a particular system, and each controller mayshare common information with another controller, or retrieve the commoninformation from a zone player, if such a zone player storesconfiguration data (e.g., such as a state variable). Further, acontroller can be integrated into a zone player.

It should be noted that other network-enabled devices such as aniPhone™, iPad™ or any other smart phone or network-enabled device (e.g.,a networked computer such as a PC or Mac™) can also be used as acontroller to interact or control zone players in a particularenvironment. In some embodiments, a software application or upgrade canbe downloaded onto a network-enabled device to perform the functionsdescribed herein.

In certain embodiments, a user can create a zone group (also referred toas a bonded zone) including at least two zone players from thecontroller 500. The zone players in the zone group can play audio in asynchronized fashion, such that all of the zone players in the zonegroup playback an identical audio source or a list of identical audiosources in a synchronized manner such that no (or substantially no)audible delays or hiccups are to be heard. Similarly, in someembodiments, when a user increases the audio volume of the group fromthe controller 500, the signals or data of increasing the audio volumefor the group are sent to one of the zone players and causes other zoneplayers in the group to be increased together in volume.

A user via the controller 500 can group zone players into a zone groupby activating a “Link Zones” or “Add Zone” soft button, or de-grouping azone group by activating an “Unlink Zones” or “Drop Zone” button. Forexample, one mechanism for ‘joining’ zone players together for audioplayback is to link a number of zone players together to form a group.To link a number of zone players together, a user can manually link eachzone player or room one after the other. For example, assume that thereis a multi-zone system that includes the following zones: Bathroom,Bedroom, Den, Dining Room, Family Room, and Foyer. In certainembodiments, a user can link any number of the six zone players, forexample, by starting with a single zone and then manually linking eachzone to that zone.

In certain embodiments, a set of zones can be dynamically linkedtogether using a command to create a zone scene or theme (subsequent tofirst creating the zone scene). For instance, a “Morning” zone scenecommand can link the Bedroom, Office, and Kitchen zones together in oneaction. Without this single command, the user would manually andindividually link each zone. The single command may include a mouseclick, a double mouse click, a button press, a gesture, or some otherprogrammed or learned action. Other kinds of zone scenes can beprogrammed or learned by the system over time.

In certain embodiments, a zone scene can be triggered based on time(e.g., an alarm clock function). For instance, a zone scene can be setto apply at 8:00 am. The system can link appropriate zonesautomatically, set specific music to play, and then stop the music aftera defined duration and revert the zones to their prior configuration.Although any particular zone can be triggered to an “On” or “Off” statebased on time, for example, a zone scene enables any zone(s) linked tothe scene to play a predefined audio (e.g., a favorable song, apredefined playlist) at a specific time and/or for a specific duration.If, for any reason, the scheduled music failed to be played (e.g., anempty playlist, no connection to a share, failed Universal Plug and Play(UPnP), no Internet connection for an Internet Radio station, and soon), a backup buzzer can be programmed to sound. The buzzer can includea sound file that is stored in a zone player, for example.

V. Playback Queue

As discussed above, in some embodiments, a zone player may be assignedto a playback queue identifying zero or more media items for playback bythe zone player. The media items identified in a playback queue may berepresented to the user via an interface on a controller. For instance,the representation may show the user (or users if more than onecontroller is connected to the system) how the zone player is traversingthe playback queue, such as by highlighting the “now playing” item,graying out the previously played item(s), highlighting the to-be-playeditem(s), and so on.

In some embodiments, a single zone player is assigned to a playbackqueue. For example, zone player 114 in the bathroom of FIG. 1 may belinked or assigned to a “Bathroom” playback queue. In an embodiment, the“Bathroom” playback queue might have been established by the system as aresult of the user naming the zone player 114 to the bathroom. As such,contents populated and identified in the “Bathroom” playback queue canbe played via the zone player 114 (the bathroom zone).

In some embodiments, a zone or zone group is assigned to a playbackqueue. For example, zone players 106 and 108 in the family room of FIG.1 may be linked or assigned to a “Family room” playback queue. Inanother example, if family room and dining room zones were grouped, thenthe new group would be linked or assigned to a family room+dining roomplayback queue. In some embodiments, the family room+dining roomplayback queue would be established based upon the creation of thegroup. In some embodiments, upon establishment of the new group, thefamily room+dining room playback queue can automatically include thecontents of one (or both) of the playback queues associated with eitherthe family room or dining room or both. In one instance, if the userstarted with the family room and added the dining room, then thecontents of the family room playback queue would become the contents ofthe family room+dining room playback queue. In another instance, if theuser started with the family room and added the dining room, then thefamily room playback queue would be renamed to the family room+diningroom playback queue. If the new group was “ungrouped,” then the familyroom+dining room playback queue may be removed from the system and/orrenamed to one of the zones (e.g., renamed to “family room” or “diningroom”). After ungrouping, each of the family room and the dining roomwill be assigned to a separate playback queue. One or more of the zoneplayers in the zone or zone group may store in memory the associatedplayback queue.

As such, when zones or zone groups are “grouped” or “ungrouped”dynamically by the user via a controller, the system will, in someembodiments, establish or remove/rename playback queues respectively, aseach zone or zone group is to be assigned to a playback queue. In otherwords, the playback queue operates as a container that can be populatedwith media items for playback by the assigned zone. In some embodiments,the media items identified in a playback queue can be manipulated (e.g.,re-arranged, added to, deleted from, and so on).

By way of illustration, FIG. 6 shows an example network 600 for mediacontent playback. As shown, the example network 600 includes examplezone players 612 and 614, example audio sources 662 and 664, and examplemedia items 620. The example media items 620 may include playlist 622,music track 624, favorite Internet radio station 626, playlists 628 and630, and album 632. In one embodiment, the zone players 612 and 614 maybe any of the zone players shown in FIGS. 1, 2, and 4. For instance,zone players 612 and 614 may be the zone players 106 and 108 in theFamily Room.

In one example, the example audio sources 662 and 664, and example mediaitems 620 may be partially stored on a cloud network, discussed morebelow in connection to FIG. 8. In some cases, the portions of the audiosources 662, 664, and example media items 620 may be stored locally onone or both of the zone players 612 and 614. In one embodiment, playlist622, favorite Internet radio station 626, and playlist 630 may be storedlocally, and music track 624, playlist 628, and album 632 may be storedon the cloud network.

Each of the example media items 620 may be a list of media itemsplayable by a zone player(s). In one embodiment, the example media itemsmay be a collection of links or pointers (i.e., URI) to the underlyingdata for media items that are stored elsewhere, such as the audiosources 662 and 664. In another embodiment, the media items may includepointers to media content stored on the local zone player, another zoneplayer over a local network, or a controller device connected to thelocal network.

As shown, the example network 600 may also include an example queue 602associated with the zone player 612, and an example queue 604 associatedwith the zone player 614. Queue 606 may be associated with a group, whenin existence, comprising zone players 612 and 614. Queue 606 mightcomprise a new queue or exist as a renamed version of queue 602 or 604.In some embodiments, in a group, the zone players 612 and 614 would beassigned to queue 606 and queue 602 and 604 would not be available atthat time. In some embodiments, when the group is no longer inexistence, queue 606 is no longer available. Each zone player and eachcombination of zone players in a network of zone players, such as thoseshown in FIG. 1 or that of example zone players 612, 614, and examplecombination 616, may be uniquely assigned to a corresponding playbackqueue.

A playback queue, such as playback queues 602-606, may includeidentification of media content to be played by the corresponding zoneplayer or combination of zone players. As such, media items added to theplayback queue are to be played by the corresponding zone player orcombination of zone players. The zone player may be configured to playitems in the queue according to a specific order (such as an order inwhich the items were added), in a random order, or in some other order.

The playback queue may include a combination of playlists and othermedia items added to the queue. In one embodiment, the items in playbackqueue 602 to be played by the zone player 612 may include items from theaudio sources 662, 664, or any of the media items 622-632. The playbackqueue 602 may also include items stored locally on the zone player 612,or items accessible from the zone player 614. For instance, the playbackqueue 602 may include Internet radio 626 and album 632 items from audiosource 662, and items stored on the zone player 612.

When a media item is added to the queue via an interface of acontroller, a link to the item may be added to the queue. In a case ofadding a playlist to the queue, links to the media items in the playlistmay be provided to the queue. For example, the playback queue 602 mayinclude pointers from the Internet radio 626 and album 632, pointers toitems on the audio source 662, and pointers to items on the zone player612. In another case, a link to the playlist, for example, rather than alink to the media items in the playlist may be provided to the queue,and the zone player or combination of zone players may play the mediaitems in the playlist by accessing the media items via the playlist. Forexample, the album 632 may include pointers to items stored on audiosource 662. Rather than adding links to the items on audio source 662, alink to the album 632 may be added to the playback queue 602, such thatthe zone player 612 may play the items on the audio source 662 byaccessing the items via pointers in the album 632.

In some cases, contents as they exist at a point in time within aplayback queue may be stored as a playlist, and subsequently added tothe same queue later or added to another queue. For example, contents ofthe playback queue 602, at a particular point in time, may be saved as aplaylist, stored locally on the zone player 612 and/or on the cloudnetwork. The saved playlist may then be added to playback queue 604 tobe played by zone player 614.

VI. Example Ad-Hoc Network

Particular examples are now provided in connection with FIG. 7 todescribe, for purposes of illustration, certain embodiments to provideand facilitate connection to a media playback system (e.g., such assystem 100 shown in FIG. 1). FIG. 7 shows that there are three zoneplayers 702, 704 and 706 and a controller 708 that form a network branchthat is also referred to as an Ad-Hoc network 710. The network 710 maybe wireless, wired, or a combination of wired and wireless technologies.In general, an Ad-Hoc (or “spontaneous”) network is a local area networkor other small network in which there is generally no one access pointfor all traffic. With an established Ad-Hoc network 710, the devices702, 704, 706 and 708 can all communicate with each other in a“peer-to-peer” style of communication, for example. Furthermore, devicesmay join and/or leave from the network 710, and the network 710 willautomatically reconfigure itself without needing the user to reconfigurethe network 710. While an Ad-Hoc network is referenced in FIG. 7, it isunderstood that a playback network may be based on a type of networkthat is completely or partially different from an Ad-Hoc network.

Using the Ad-Hoc network 710, the devices 702, 704, 706, and 708 canshare or exchange one or more audio sources and be dynamically grouped(or ungrouped) to play the same or different audio sources. For example,the devices 702 and 704 are grouped to playback one piece of music, andat the same time, the device 706 plays back another piece of music. Inother words, the devices 702, 704, 706 and 708, as shown in FIG. 7, forma HOUSEHOLD that distributes audio and/or reproduces sound. As usedherein, the term HOUSEHOLD (provided in uppercase letters todisambiguate from the user's domicile) is used to represent a collectionof networked devices that are cooperating to provide an application orservice. An instance of a HOUSEHOLD is identified with a household 710(or household identifier), though a HOUSEHOLD may be identified with adifferent area or place.

In certain embodiments, a household identifier (HHID) is a short stringor an identifier that is computer-generated to help ensure that it isunique. Accordingly, the network 710 can be characterized by a uniqueHHID and a unique set of configuration variables or parameters, such aschannels (e.g., respective frequency bands), service set identifier(SSID) (a sequence of alphanumeric characters as a name of a wirelessnetwork), and WEP keys (wired equivalent privacy) or other securitykeys. In certain embodiments, SSID is set to be the same as HHID.

In certain embodiments, each HOUSEHOLD includes two types of networknodes: a control point (CP) and a zone player (ZP). The control pointcontrols an overall network setup process and sequencing, including anautomatic generation of required network parameters (e.g., securitykeys). In an embodiment, the CP also provides the user with a HOUSEHOLDconfiguration user interface. The CP function can be provided by acomputer running a CP application module, or by a handheld controller(e.g., the controller 308) also running a CP application module, forexample. The zone player is any other device on the network that isplaced to participate in the automatic configuration process. The ZP, asa notation used herein, includes the controller 308 or a computingdevice, for example. In some embodiments, the functionality, or certainparts of the functionality, in both the CP and the ZP are combined at asingle node (e.g., a ZP contains a CP or vice-versa).

In certain embodiments, configuration of a HOUSEHOLD involves multipleCPs and ZPs that rendezvous and establish a known configuration suchthat they can use a standard networking protocol (e.g., IP over Wired orWireless Ethernet) for communication. In an embodiment, two types ofnetworks/protocols are employed: Ethernet 802.3 and Wireless 802.11g.Interconnections between a CP and a ZP can use either of thenetworks/protocols. A device in the system as a member of a HOUSEHOLDcan connect to both networks simultaneously.

In an environment that has both networks in use, it is assumed that atleast one device in a system is connected to both as a bridging device,thus providing bridging services between wired/wireless networks forothers. The zone player 706 in FIG. 7 is shown to be connected to bothnetworks, for example. The connectivity to the network 712 is based onEthernet and/or Wireless, while the connectivity to other devices 702,704 and 708 is based on Wireless and Ethernet if so desired.

It is understood, however, that in some embodiments each zone player706, 704, 702 may access the Internet when retrieving media from thecloud (e.g., the Internet) via the bridging device. For example, zoneplayer 702 may contain a uniform resource locator (URL) that specifiesan address to a particular audio track in the cloud. Using the URL, thezone player 702 may retrieve the audio track from the cloud, andultimately play the audio out of one or more zone players.

VII. Another Example System Configuration

FIG. 8 shows a system 800 including a plurality of interconnectednetworks including a cloud-based network and at least one media playbacksystem (e.g., like system 100 in FIG. 1). The at least one mediaplayback system includes a plurality of playback devices or players,though it is understood that the playback network may contain only oneplayback device. In certain embodiments, each player has an ability toretrieve its content for playback. Control and content retrieval can bedistributed or centralized, for example. Input can include streamingcontent provider input, third party application input, mobile deviceinput, user input, and/or other playback network input into the cloudfor local distribution and playback.

As illustrated by the example system 800 of FIG. 8, a plurality ofcontent providers 820-850 can be connected to one or more local playbacknetworks 860-870 via a cloud and/or other network 810. Using the cloud810, a multimedia audio system server 820 (e.g., Sonos™), a mobiledevice 830, a third party application 840, a content provider 850 and soon can provide multimedia content (requested or otherwise) to localplayback networks 860, 870. Within each local playback network 860, 870,a controller 862, 872 and a playback device 864, 874 can be used toplayback audio content.

VIII. Volume Enhancement Embodiments

As described above, in some embodiments, various systems illustratedabove advantageously allow for dynamic user configuration of one or morezone groups between two or more zone players for each group. Groups ofvarying size can be constructed and destructed upon command. In someembodiments, each group includes a group volume and each zone player ofthe group may have its own, individual volume setting, which is based onchanges in the group volume. As such, changing a group volume may causea direct change to a zone player volume setting (and vice-versa) andaffect playback even when the zone player is no longer a part of thegroup. In the embodiments described herein, to improve the userexperience in grouping and ungrouping zone players, volume settings ofthe zone players are more intelligently applied by the system.

FIG. 9 shows an example system 900 that includes zone player 902, zoneplayer 904, zone player 910, and controller 906. The example system 900is intended to be illustrative only, and can include more or lesscomponents like zone players and controllers, such as described withrespect to the earlier figures above. Additionally, it is understoodthat zone players 902, 904, and 910 can play audio independently or ingroups as described above.

Now turning to method 1000 of FIG. 10 in view of system 900 shown inFIG. 9, a volume level is established for an ungrouped zone player atblock 1002 in FIG. 10. To illustrate, assume that zone player 902 iscurrently not part of a synchronous audio playback group and a volumelevel is set for audio playback. The volume level may be input by a userinto controller 906 and then transmitted from controller 906 to zoneplayer 902 using, for example, a wired or wireless network technology908, such as described above. Alternatively, the volume level may beinput by a user on the zone player 902 directly using an interface onthe zone player 902 if such an interface exists.

Before continuing with the example, it should be understood that a zonemay be a bonded zone as described above, and as such the zone maycomprise more than a single zone player. In an instance when a zonecomprises two or more zone players (e.g., paired or consolidated), thevolume level for the zone may be similarly established at block 1002 (asif the zone is a single zone player). According to one example, a stereopairing between two zone players might have a single volume level forthe pair. According to another example, a group containing twofull-range audio playing zone players might have a single volume levelfor the group. As such, a “zone” may be substituted for a “zone player”in the figures and corresponding description.

According to block 1004, in one embodiment, the volume level is storedin memory of zone player 902. In another embodiment, the volume level isstored in memory of controller 906. In yet another embodiment, thevolume level is stored at a remote server (not shown in FIG. 9). In someembodiments, the volume level may be stored on more than one device.Irrespective of which device or devices store the volume level for zoneplayer 902, the zone player 902 is configured to retrieve and use thestored volume level when commanded to play audio.

According to block 1006, the zone player for which the volume level hasbeen established and stored per blocks 1002 and 1004 is now grouped toanother zone player. In the example of FIG. 9, zone player 902 isgrouped with zone player 904 to synchronously playback audio (e.g.,dining room 104 in FIG. 1 is grouped with kitchen 102). The command togroup the zone players may be input by the user into controller 906 andthen transmitted to any or all of zone players 902 and 904 using wiredor wireless network technology 908, such as described above. At anytime, the volume level for zone player 902 may change due to a directchange to the volume level setting for zone player 902 (while in thegroup) or to a group volume level change.

At block 1008, the zone player is removed from the group established in1006. In the example of FIG. 9, we can assume zone player 902 is nowremoved from the group consisting of zone players 902 and 904. A commandto remove the zone player 902 from the group may be input by the userinto controller 906 and then transmitted to any or all of zone players902 and 904 using wired or wireless network technology 908, such asdescribed above.

At block 1010, the volume setting for zone player 902 is restored to thestored volume level per block 1004. In other words, the volume for audioplayback by the now ungrouped zone player 902 is set back to the volumelevel just prior to grouping. In one embodiment, the zone player 902retrieves the stored volume level from memory and makes the adjustment.In one embodiment, the zone player 902 may verify first whether a changein volume has occurred since the last ungrouping, and if not, then thevolume setting is left alone. In another embodiment, the zone player 902may simply override the volume setting regardless of whether the volumechanged since the last ungrouping. In yet another embodiment, the zoneplayer 902 may determine whether it is continuing to play the music ofthe group as a stand-alone player, and if so, then the volume setting isleft alone. In this embodiment, the volume level that is stored for thezone player may be updated to reflect the current volume level.

FIG. 11 shows another method 1100 to consider in view of system 900 ofFIG. 9. Let us assume that zone players 902 and 904 are now grouped(e.g., see also block 1006 of FIG. 10 to see when the two zone playerswere grouped in that example). At block 1102, a volume level for thegroup is established and can even change upon a user's request for theduration of the group. When a volume level is set for the group, or zoneplayer 902 while in the group, then the volume level for zone player 902and the associated group is stored per block 1104. Information may bestored in a table that identifies the particular group (e.g., a groupconsisting of zone players 902 and 904) and the volume setting for zoneplayer 902.

Per block 1106, the zone player 902 is removed from the group formed perthe example of FIG. 11. By way of illustration, one decides to ungroupthe kitchen 102 in FIG. 1 from the dining room 104 to listen to music inthe kitchen 102 without playing the audio in the dining room 104.

Subsequently, let us assume that the zone player 902 is regrouped withzone player 904 per block 1108. Responsively, the system identifies thatthe group is established and restores the volume setting for zone player902 to the stored value for the group. In another embodiment, the zoneplayer 902 may determine whether it is continuing to play the music ofthe stand-alone player as the group music, and if so, then the volumelevel setting for zone player 902 is left alone and the volume levelsetting for the group is adjusted based on the volume level for the zoneplayer 902.

In some embodiments, as groups are formed, the table includes the groupsand the volume level settings for the zone player or each zone player ifthe table is universally shared among the system. An example tableshowing volume settings for zone player 902 by itself and in variousgroup configurations is shown below (the table entries are onlyillustrative and may comprises shorter and/or different entries):

Zone Configuration Volume Level Setting Zone player 902 50% Zone player902 in group consisting of zone 35% players 902 and 904 Zone player 902in group consisting of zone 32% players 902, 904, and 906

Looking to the table above, when the zone player 902 is playing audio byitself, the volume level is set to 50% until a change by a user is made.If a change is made, then the table can be updated to reflect thechange. When the zone player 902 is grouped with zone player 904, thenthe volume level for zone player 902 is set to 35% until a change, ifany, is made by the user. Similarly, when the zone player 902 is groupedwith zone players 904 and 906, then the volume level for zone player 902is set to 32% until a change, if any, is made by the user.

As described above, in some embodiments, a zone may be substituted forzone player. To illustrate, kitchen 102 in FIG. 1 might be substitutedfor zone player 902, dining room for zone player 904, and family roomfor zone player 906. When playing audio in the kitchen zone, the audiowould be set to 50% according to the table above. When playing the sameaudio in the kitchen zone and the dining room zone, the kitchen zonevolume level would be set to 35%. When playing the same audio across thekitchen, dining room, and family room zones, the kitchen volume levelwould be set to 32%.

In a similar manner, the group volume for specific groups may be stored.Recall that in some embodiments a zone player volume is determined basedon the group volume (if the zone player is grouped). That is, a changeto the group volume affects the individual zone player volumes, and insome embodiments, a change to the individual zone player volumes mayaffect the group volume. In some embodiments, the group volume may beused along with other volume settings to derive, for example, a volumelevel for a newly added player to a group. The user can still change thenew player's volume level, but it provides a best guess as to anappropriate volume level. The new group information can further bestored in the table.

In the examples described above, the volume levels referred mostly to anabsolute volume level. In some embodiments, the volume level may insteadrefer to a proportion of volume to other players in a particular group.For example, based on historical volume level setting data, a table maycontain information that zone player 902 is to be set to 20% less volumethan zone player 904. Then, when the group consisting of zone payers 902and 904 is established (again), one of the players can adjust its volumelevel relative to the device being joined with. In this example, thevolume level of the first zone player in the group can be used as thebase and the volume level of the second zone player is determined usingthe proportion value and the volume level of the first zone player. Assuch, either zone player 902 or 904 could be used as the base dependingon how the user forms the group. An advantage of using the first zoneplayer in the group as the base allows the user to set the group volumebased on the volume setting of the zone player(s) that he or she islikely hearing at the time of group formation (e.g., the user is in theliving room and starts with the living room zone player to form agroup). The proportional values can change as the user changes thevolume levels for the zone players in the group.

A table below shows an example for proportional volume settings. Thetable may include information for a particular zone player (as shownbelow), in which case, each zone player would be associated with its owntable. In another embodiment, a table may include the volume informationfor all of the zone players in a system. In the table below, if a zonegroup is started with zone player 904 and zone player 902 is added, thenthe volume level for zone player 902 is set to 10% of the current volumesetting of zone player 904. Similarly, if a group includes more than twozone players, then volume settings in relation to the other players canbe included, such as shown below with respect to group containing zoneplayers 902, 904, and 906. In this example, the volume setting for zoneplayer 902 need only be set relative to one of the players in the group(e.g., either 904 or 906), and that player may be selected, for example,based on the order in which the group was formed, based on a random orpseudo-random selection, or some other method.

Zone Configuration Volume Setting Zone player 902 in group consisting ofzone 10% relative to zone players 902 and 904 player 904 Zone player 902in group consisting of zone 11% relative to zone players 902, 904, and906 player 904 13% relative to zone player 906

It is understood that information pertaining to both absolute volumelevels and proportional volumes may be used together. In one example,assume that a system is programmed to perform the following: when agroup is re-formed, the volume level of the first zone player in thegroup is set to a previously stored value (an absolute volume level) andthe other zone player(s) are set in proportion to the first zone player.In another example, assume that a system is programmed to perform thefollowing: the volume level for each zone player in a group is set toits stored volume level (their individual, absolute volume levels), buta change to any one of the zone players affects the volume setting ofthe other zone players based on the proportional volume level. Theinformation pertaining to both types of volume settings can be stored ina table for reference by the system.

It is also understood that a table, or some other similarly suitablestoring/organizing mechanism, may be stored locally in memory at eachzone player, locally in memory at a selected one or more zone players,locally in memory at one or more controllers, or in memory at a remoteserver(s) that is accessible by the system. In some embodiments, eachzone player stores only its associated volume setting information. Insome embodiments, each zone player stores volume setting information foritself and other zone players in the system. In some embodiments, volumesetting information is passed around the system (e.g., in a round-robinfashion; e.g., on an as-needed basis).

In another embodiment, when grouping zone players, the volume level ofthe zone players are set to the base zone player. For example, assumethat zone player 902 has a current volume level of 30% and zone player904 has a current volume level of 55%. When a user groups zone players902 and 904, starting with zone player 902, then the volume level ofzone player 904 is modified to 30%, which is the same as the volumelevel of zone player 902.

FIG. 12 shows an example method 1200 for setting volume levels in agroup according to this embodiment. At block 1202, a group isestablished between two or more zone players. At block 1204, a groupcoordinator is identified. In some embodiments, the group coordinator,or base zone player, is the first zone player in the group formation. Insome embodiments, the base zone player is the zone player with thelowest volume setting (or alternatively, the highest volume setting orsome other predefined volume level). At block 1206, the volume level ofeach zone player is set to the base zone player volume.

In an alternative embodiment, the volume level of each zone player isset to a predefined volume level. For example, each zone player may beset to a volume level previously set by the user for group volume. Inanother example, each zone player may be set to a volume level based ona historical number, such as an average group volume level.

In the embodiments described above, it is possible for a zone player tohave a volume level setting without playing audio. When the zone playeris used for audio playback, the zone player will use the volume levelunless otherwise changed by the user.

IX. Conclusion

The description above discloses various example systems, methods,apparatus, and articles of manufacture including, among othercomponents, firmware and/or software executed on hardware. However, suchexamples are merely illustrative and should not be considered aslimiting. For example, it is contemplated that any or all of thesefirmware, hardware, and/or software components can be embodiedexclusively in hardware, exclusively in software, exclusively infirmware, or in any combination of hardware, software, and/or firmware.Accordingly, while the following describes example systems, methods,apparatus, and/or articles of manufacture, the examples provided are notthe only way(s) to implement such systems, methods, apparatus, and/orarticles of manufacture.

As indicated above, the present application and the inventions describedherein involve numerous volume enhancement embodiments that can beapplied to a multi-zone player system that is capable of establishingsynchronous audio playback groups amongst zone players. In one aspect, amethod is provided. In one instance, the method involves establishing asynchronous audio playback group between a first zone player and atleast a second zone player; receiving a first volume level for the firstzone player for audio playback in the synchronous audio playback group;and storing the first volume level associated with the first zone playerand the synchronous audio playback group, wherein the stored firstvolume level is used by the first zone player in a subsequent groupingbetween the first and second zone players.

Another method includes receiving a volume level for a zone player priorto grouping, where the zone player is configured to play audio accordingto the volume level; and storing the volume level prior to grouping,wherein the volume level is used by the zone player when the zone playeris removed from the synchronous audio playback group.

Yet another method includes establishing a synchronous audio playbackgroup between a first zone player, a second zone player, and a thirdzone player; receiving a second volume level for the first zone playerwhile in the synchronous audio playback group comprising the first,second, and third zone players; storing the second volume levelassociated with the first zone player and the synchronous playback groupcomprising the first, second, and third zone players, wherein the storedsecond volume level is used by the first zone player in a subsequentgrouping between the first, second, and third zone players.

In another aspect, a system is provided. The system includes zoneplayers and controllers for establishing a synchronous audio playbackgroup between a first zone player and at least a second zone player;receiving a first volume level for the first zone player for audioplayback in the synchronous audio playback group; and storing the firstvolume level associated with the first zone player and the synchronousaudio playback group, wherein the stored first volume level is used bythe first zone player in a subsequent grouping between the first andsecond zone players.

In yet another aspect, a non-transitory computer readable memory isprovided. The non-transitory computer readable memory has stored thereoninstructions executable by a computing device to cause the computingdevice to perform functions. The functions include establishing asynchronous audio playback group between a first zone player and atleast a second zone player; receiving a first volume level for the firstzone player for audio playback in the synchronous audio playback group;and storing the first volume level associated with the first zone playerand the synchronous audio playback group, wherein the stored firstvolume level is used by the first zone player in a subsequent groupingbetween the first and second zone players.

Additionally, references herein to “embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment can be included in at least one example embodiment of theinvention. The appearances of this phrase in various places in thespecification are not necessarily all referring to the same embodiment,nor are separate or alternative embodiments mutually exclusive of otherembodiments. As such, the embodiments described herein, explicitly andimplicitly understood by one skilled in the art, can be combined withother embodiments.

The specification is presented largely in terms of illustrativeenvironments, systems, procedures, steps, logic blocks, processing, andother symbolic representations that directly or indirectly resemble theoperations of data processing devices coupled to networks. These processdescriptions and representations are typically used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art. Numerous specific details are set forth to provide athorough understanding of the present disclosure. However, it isunderstood to those skilled in the art that certain embodiments of thepresent disclosure can be practiced without certain, specific details.In other instances, well known methods, procedures, components, andcircuitry have not been described in detail to avoid unnecessarilyobscuring aspects of the embodiments. Accordingly, the scope of thepresent disclosure is defined by the appended claims rather than theforgoing description of embodiments.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible mediumsuch as a memory, DVD, CD, Blu-ray, and so on, storing the softwareand/or firmware.

We claim:
 1. A first playback device comprising: a network interface;one or more speakers; one or more processors; and tangible,non-transitory, computer-readable media having instructions encodedtherein, wherein the instructions, when executed by the one or moreprocessors, cause the playback device to perform a method comprising:playing, via the one or more speakers, audio content at a first volumelevel as part of a first audio playback group configuration comprisingthe first playback device and a second playback device configured toplay back in synchrony; storing in a data storage, the first volumelevel in association with the first audio playback group configuration;joining a second audio playback group configuration, wherein the secondaudio playback group configuration excludes the second playback device;adjusting the playback device to play audio content at a second volumelevel as part of the second audio playback group configuration; whilethe first playback device is playing audio at the second volume level aspart of the second audio playback group configuration, receiving, viathe network interface, a command to play audio content as part of thefirst audio playback group configuration; and in response to receivingthe command to play audio as part of the first audio playback groupconfiguration: (i) joining the first audio playback group configuration,(ii) identifying the first volume level in the data storage; and (iii)adjusting the first playback device to play audio content at theidentified first volume level as part of the first audio playback groupconfiguration.
 2. The first playback device of claim 1, wherein playingaudio content at the second volume level as part of the second audioplayback group configuration comprises playing a particular audio track,and wherein the command to play audio as part of the first audioplayback group configuration comprises a command to play a differentaudio track.
 3. The first playback device of claim 1, wherein the methodfurther comprises: before playing audio content at the first volumelevel as part of the first audio playback group configuration and beforejoining the second audio playback group configuration, receiving, viathe network interface, a command to join the first audio playback groupconfiguration; and receiving a command to adjust the first playbackdevice to play audio content at the first volume level.
 4. The firstplayback device of claim 1, wherein the method further comprises:identifying, in the data storage, the second volume in association withthe second audio playback group configuration, and wherein the firstplayback device adjusts the first playback device to play audio contentat the second volume level as part of the second audio playback groupconfiguration in response to identifying, in the data storage, thesecond volume in association with the second audio playback groupconfiguration.
 5. The first playback device of claim 1, wherein themethod further comprises: receiving a command to play audio content atthe second volume level, and wherein the first playback device adjuststhe first playback device to play audio content at the second volumelevel as part of the second audio playback group configuration inresponse to receiving the command to play audio content at the secondvolume level.
 6. The first playback device of claim 1, wherein thesecond audio playback group configuration comprises the first playbackdevice and a third playback device.
 7. The first playback device ofclaim 1, wherein the second audio playback group configuration consistsof the first playback device.
 8. The first playback device of claim 1,wherein the method further comprises: determining the second volumelevel based on a volume level of a group coordinator of the second audioplayback group configuration, and wherein the first playback deviceadjusts the first playback device to play audio content at the secondvolume level as part of the second audio playback group configuration inresponse to determining the second volume level based on the volumelevel of a group coordinator of the second audio playback group.
 9. Anon-transitory computer-readable medium having instructions encodedtherein, wherein the instructions, when executed by one or moreprocessors, cause a first playback device to perform a functionscomprising: playing, via one or more speakers, audio content at a firstvolume level as part of a first audio playback group configurationcomprising the first playback device and a second playback deviceconfigured to play back in synchrony; storing in a data storage, thefirst volume level in association with the first audio playback groupconfiguration; joining a second audio playback group configuration,wherein the second audio playback group configuration excludes thesecond playback device; adjusting the playback device to play audiocontent at a second volume level as part of the second audio playbackgroup configuration; while the first playback device is playing audio atthe second volume level as part of the second audio playback groupconfiguration, receiving, via a network interface of the playbackdevice, a command to play audio content as part of the first audioplayback group configuration; and in response to receiving the commandto play audio as part of the first audio playback group configuration:(i) joining the first audio playback group configuration, (ii)identifying the first volume level in the data storage; and (iii)adjusting the first playback device to play audio content at theidentified first volume level as part of the first audio playback groupconfiguration.
 10. The non-transitory computer-readable medium of claim9, wherein playing audio content at the second volume level as part ofthe second audio playback group configuration comprises playing aparticular audio track, and wherein the command to play audio as part ofthe first audio playback group configuration comprises a command to playa different audio track.
 11. The non-transitory computer-readable mediumof claim 9, wherein the functions further comprise: before playing audiocontent at the first volume level as part of the first audio playbackgroup configuration and before joining the second audio playback groupconfiguration, receiving, via the network interface, a command to jointhe first audio playback group configuration; and receiving a command toadjust the playback device to play audio content at the first volumelevel.
 12. The non-transitory computer-readable medium of claim 9,wherein the functions further comprise: identifying, in the datastorage, the second volume in association with the second audio playbackgroup configuration, and wherein the first playback device adjusts thefirst playback device to play audio content at the second volume levelas part of the second audio playback group configuration in response toidentifying, in the data storage, the second volume in association withthe second audio playback group configuration.
 13. The non-transitorycomputer-readable medium of claim 9, wherein the second audio playbackgroup configuration comprises the first playback device and a thirdplayback device.
 14. The non-transitory computer-readable medium ofclaim 9, wherein the second audio playback group configuration consistsof the first playback device.
 15. The non-transitory computer-readablemedium of claim 9, wherein the functions further comprise: receiving acommand to play audio content at the second volume level, and whereinthe first playback device adjusts the first playback device to playaudio content at the second volume level as part of the second audioplayback group configuration in response to receiving the command toplay audio content at the second volume level.
 16. A method comprising:playing, via a first playback device, audio content at a first volumelevel as part of a first audio playback group configuration comprisingthe first playback device and a second playback device configured toplay back in synchrony; storing, via the first playback device in a datastorage, the first volume level in association with the first audioplayback group configuration; joining, by the first playback device, asecond audio playback group configuration, wherein the second audioplayback group configuration excludes the second playback device;playing, via the first playback device, audio content at a second volumelevel as part of the second audio playback group configuration; whilethe first playback device is playing audio at the second volume level aspart of the second audio playback group configuration, receiving, via anetwork interface of the first playback device, a command to play audiocontent as part of the first audio playback group configuration; and inresponse to receiving the command to play audio as part of the firstaudio playback group configuration: the playback device (i) joining thefirst audio playback group configuration: (i) joining the first audioplayback group configuration, (ii) identifying the first volume level inthe data storage; and playing audio content at the identified firstvolume level as part of the first audio playback group configuration.17. The method of claim 16, wherein playing audio content at the secondvolume level as part of the second audio playback group configurationcomprises playing a particular audio track and wherein the command toplay audio as part of the first audio playback group configurationcomprises a command to play a different audio track.
 18. The method ofclaim 16, further comprising: receiving a command to join the firstaudio playback group configuration; and receiving a command to adjustthe playback device to play audio content at the first volume level, andwherein the first playback device plays audio content at the secondvolume level as part of the second audio playback group configuration inresponse to receiving the command to play audio content at the secondvolume level.
 19. The method of claim 16, further comprising:identifying, in the data storage, the second volume in association withthe second audio playback group configuration, and wherein the firstplayback device plays audio content at the second volume level as partof the second audio playback group configuration in response toidentifying, in the data storage, the second volume in association withthe second audio playback group configuration.
 20. The method of claim16, wherein the second audio playback group configuration comprises thefirst playback device and a third playback device.
 21. The method ofclaim 16, wherein the second audio playback group configuration consistsof the first playback device.